home *** CD-ROM | disk | FTP | other *** search
- Date: 11 Jan 1996 12:49:22 EST
- Path: gcomm.com!jackal
- Newsgroups: comp.lang.c
- From: jackal@gcomm.com (Jack Alvrus)
- Message-ID: <8213825629501@demosys.gcomm.com>
- Organization: Galacticomm, Inc.
- References: <TANMOY.96Jan10212912@qcd.lanl.gov>
- Subject: Re: stricmp()
-
-
- TA>A rare post with so many wrong assumptions!!! :-)
-
- Well, if they're wrong it's a good thing I made this post to find out,
- eh? :)
-
- TA> stricmp() is an ANSI library function, right? So it should exhibit, if
-
- TA>no.
-
- So far that's been the overwhelming response, and if that is in fact
- correct that's fine. I do not have access to a copy of the ANSI C spec
- so I cannot verify this for myself, however, the Borland C++ v4.5
- Library Reference manual states that stricmp() is "defined by the ANSI C
- standard." Perhaps someone should notify Borland?
-
- TA> not consistent, at least *documented* behavior, right?
-
- TA>no and no. Usually library functions have certain requirments on their
- TA>parameters, and a violation of these can lead to undefined behaviour,
- TA>which need neither be consistent nor documented.
-
- Ah, but the requirements ARE documented. If, under certain conditions,
- behavior is undefined, then if those conditions are documented the
- behavior is also documented. These conditions are part of what I'm
- trying to find out.
-
- TA>Any use of an object with external linkage leads to undefined
- TA>behaviour if the implementation does not explicitly permit and
- TA>define such use.
-
- Are you sure you aren't a lawyer? :)
-
- Thanks for your response.
-
- Jack Alvrus
- Galacticomm Software Engineer
-